Usage Note 69631: The error "An error occurred executing the workspace job "".Timeout during initialization" occurs in SAS® Enterprise Guide®
When you connect to a workspace server locally or remotely, the following error can occur:
An error occurred executing the workspace job "".
Timeout during initialization.
Problem
Custom code that is defined in Tools ► Options ► select SAS Programs ► Submit SAS code when server is connected causes the custom code to stop processing. The Submit SAS code when server is connected option automatically submits custom SAS code when a connection to a workspace server is made.
Workaround
- Open SAS® Enterprise Guide® and go to Tools ► Options ► select SAS Programs ► clear the option Submit SAS code when server is connected ► OK.
- Test the connection to the workspace server again. If the connection is successful, the code in Submit SAS code when server is connected was the cause of the issue.
- Troubleshoot the code in Submit SAS code when server is connected at this point. Paste the code from Submit SAS code when server is connected in a new program and submit the code line-by-line (highlighting the code).
- Typically, LIBNAME statements to remote databases are what causes the code to stop processing, which indicates that there is an issue with the databases. In these cases, contact the database administrators to assist with resolving the connection issues to the databases.
If the error continues to occur, complete the steps in Enabling logging in SAS® Enterprise Guide® 7.1 and later (SAS KB0036457), replicate the error and Contact SAS Technical Support for further assistance. When you use the Submit a Support Request or Create a new support request via email forms, include the SAS Enterprise Guide log that was created.
Operating System and Release Information
SAS System | SAS Enterprise Guide | Microsoft® Windows® for x64 | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows 8 Enterprise 32-bit | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows 8 Enterprise x64 | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows 8 Pro 32-bit | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows 8 Pro x64 | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows 8.1 Enterprise 32-bit | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows 8.1 Enterprise x64 | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows 8.1 Pro 32-bit | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows 8.1 Pro x64 | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows 10 | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows 11 | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows Server 2003 Datacenter Edition | 4.2 | | | |
Microsoft Windows Server 2003 Enterprise Edition | 4.2 | | | |
Microsoft Windows Server 2003 Standard Edition | 4.2 | | | |
Microsoft Windows Server 2003 for x64 | 4.2 | | | |
Microsoft Windows Server 2008 | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows Server 2008 R2 | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows Server 2008 for x64 | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows Server 2012 Datacenter | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows Server 2012 R2 Datacenter | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows Server 2012 R2 Std | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows Server 2012 Std | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows Server 2016 | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows Server 2019 | 4.2 | 8.3 | | 9.4 TS1M7 |
Microsoft Windows Server 2022 | 4.2 | 8.3 | | 9.4 TS1M7 |
Windows 7 Enterprise 32 bit | 4.2 | 8.3 | | 9.4 TS1M7 |
Windows 7 Enterprise x64 | 4.2 | 8.3 | | 9.4 TS1M7 |
Windows 7 Home Premium 32 bit | 4.2 | 8.3 | | 9.4 TS1M7 |
Windows 7 Home Premium x64 | 4.2 | 8.3 | | 9.4 TS1M7 |
Windows 7 Professional 32 bit | 4.2 | 8.3 | | 9.4 TS1M7 |
Windows 7 Professional x64 | 4.2 | 8.3 | | 9.4 TS1M7 |
Windows 7 Ultimate 32 bit | 4.2 | 8.3 | | 9.4 TS1M7 |
Windows 7 Ultimate x64 | 4.2 | 8.3 | | 9.4 TS1M7 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Date Modified: | 2022-11-17 16:22:09 |
Date Created: | 2022-10-18 12:06:14 |